Uploaded image for project: 'WORKTERRA'
  1. WORKTERRA
  2. WT-8829

Workterra field mapping definitions

    Details

    • Type: Support Activity
    • Status: Closed
    • Priority: Medium
    • Resolution: Done
    • Affects Version/s: None
    • Fix Version/s: None
    • Component/s: BenAdmin
    • Labels:
      None
    • Support Task Type:
      Query Resolution
    • Reported by:
      Support
    • Module:
      Platform
    • Severity:
      Simple

      Description

      Attached [^Field Mapping Definitions - 20160712.xls] is the field mapping definitions we have currently. Would it be possible to get an updated data dictionary for the Workterra fields.

      Cc: Abhay Patil Amit Thorve

        Attachments

          Issue Links

            Activity

            Hide
            satyap Satya added a comment -

            Hi Lalit,

            Can you please share updated data dictionary information with Cindy?
            Vinayak Kulkarni, Suraj Sokasane, Ganesh Sadawarte Hrishikesh Deshpande will help you in finding list of all columns getting used in Export/Import template.

            Let me know in case any query.

            Regards,
            Satya Prakash

            Show
            satyap Satya added a comment - Hi Lalit, Can you please share updated data dictionary information with Cindy? Vinayak Kulkarni , Suraj Sokasane , Ganesh Sadawarte Hrishikesh Deshpande will help you in finding list of all columns getting used in Export/Import template. Let me know in case any query. Regards, Satya Prakash
            Hide
            lalit.kumar Lalit Kumar (Inactive) added a comment -

            Hello Cindy Wibbing

            The updated data dictionary is attached to the ticket. Please click [here |^Field Mapping Definitions - 20170316.xls] to download the sheet.

            Fields #365 to #378 are added in the sheet.

            Fields #258 to #268 are updated in the sheet.

            CC: Satya,Vijay Siddha,Rakesh Roy

            Regards
            Lalit Kumar

            Show
            lalit.kumar Lalit Kumar (Inactive) added a comment - Hello Cindy Wibbing The updated data dictionary is attached to the ticket. Please click [here |^Field Mapping Definitions - 20170316.xls] to download the sheet. Fields #365 to #378 are added in the sheet. Fields #258 to #268 are updated in the sheet. CC: Satya , Vijay Siddha , Rakesh Roy Regards Lalit Kumar
            Hide
            Cindy.Wibbing Cindy Wibbing (Inactive) added a comment -

            Thank you!!

            Show
            Cindy.Wibbing Cindy Wibbing (Inactive) added a comment - Thank you!!
            Hide
            abhay.patil Abhay Patil (Inactive) added a comment -

            Satya thanks for sharing the data dictionary. I have a few questions, it would be great if you could respond.

            (1) Can you please specify the "nature". E.g. as I understand the field source/ nature can be of the following types.

            • Direct field from the database - from demographics (e.g. Subscriber SSN), enrollment (Enrollment effective date) etc.
            • Derived or conditional field (macro?) - i.e. it is derived by consulting a set of direct fields
            • Behavior - i.e. it doesn't give a value, but changes formatting behavior (e.g. Remove Trailing Comma, Multiple Child Seq Indicator).

            (2) Whether the field is amenable to data transformation or not. When one goes to data transformation, ONLY the fields that are amenable to data transformation show up. It will be good to know about this property.

            (3) At most places the description is too cryptic. We would like to have description that is good enough to go into a user manual. E.g. in one case it says ""Used on Custom Template Do not Use Returns employee cost for respective plan".

            Thanks,

            CC Cindy Wibbing Umesh Kanade Samir

            Show
            abhay.patil Abhay Patil (Inactive) added a comment - Satya thanks for sharing the data dictionary. I have a few questions, it would be great if you could respond. (1) Can you please specify the "nature". E.g. as I understand the field source/ nature can be of the following types. Direct field from the database - from demographics (e.g. Subscriber SSN), enrollment (Enrollment effective date) etc. Derived or conditional field (macro?) - i.e. it is derived by consulting a set of direct fields Behavior - i.e. it doesn't give a value, but changes formatting behavior (e.g. Remove Trailing Comma, Multiple Child Seq Indicator). (2) Whether the field is amenable to data transformation or not. When one goes to data transformation, ONLY the fields that are amenable to data transformation show up. It will be good to know about this property. (3) At most places the description is too cryptic. We would like to have description that is good enough to go into a user manual. E.g. in one case it says ""Used on Custom Template Do not Use Returns employee cost for respective plan". Thanks, CC Cindy Wibbing Umesh Kanade Samir
            Hide
            abhay.patil Abhay Patil (Inactive) added a comment -

            Satya - can you please also share the data model - i.e. database tables and their relationship (primary and foreign keys) as discussed in our last meeting? Thanks!

            Show
            abhay.patil Abhay Patil (Inactive) added a comment - Satya - can you please also share the data model - i.e. database tables and their relationship (primary and foreign keys) as discussed in our last meeting? Thanks!
            Hide
            satyap Satya added a comment -

            Hi Abhay,

            Yes, we will share these informations for data dictionary & more explanation for fields.

            Regards,
            Satya Prakash

            Cc: Samir Umesh Kanade Vijay Siddha Indraprakash Tiwari Lalit Kumar Rakesh Roy Vinayak Kulkarni

            Show
            satyap Satya added a comment - Hi Abhay, Yes, we will share these informations for data dictionary & more explanation for fields. Regards, Satya Prakash Cc: Samir Umesh Kanade Vijay Siddha Indraprakash Tiwari Lalit Kumar Rakesh Roy Vinayak Kulkarni
            Hide
            satyap Satya added a comment -

            Hi Lalit,

            Let's discuss to modify our previously shared document.

            Regards,
            Satya Prakaksh

            Show
            satyap Satya added a comment - Hi Lalit, Let's discuss to modify our previously shared document. Regards, Satya Prakaksh
            Hide
            satyap Satya added a comment -

            Hi Abhay Patil,

            Please find attached two modified documents:

            #1 - 'Specifiying nature of fields' and #2 - 'amenable to data transformation' have been done today along with Updates in Data dictionary, however #3 - to update field description is in progress and we will be sharing that in next week (before 04/14).

            Please let us know in case more details required.

            Thanks & Regards,
            Satya Prakash

            Cc: Cindy Wibbing Umesh Kanade Samir Vijay Siddha Lalit Kumar

            Show
            satyap Satya added a comment - Hi Abhay Patil , Please find attached two modified documents: Data Dictionary with constraints and reference key.xlsx [^Field Mapping Definitions - 20170407.xls] #1 - 'Specifiying nature of fields' and #2 - 'amenable to data transformation' have been done today along with Updates in Data dictionary, however #3 - to update field description is in progress and we will be sharing that in next week (before 04/14). Please let us know in case more details required. Thanks & Regards, Satya Prakash Cc: Cindy Wibbing Umesh Kanade Samir Vijay Siddha Lalit Kumar
            Hide
            lalit.kumar Lalit Kumar (Inactive) added a comment -

            Hello [Abhay Patil,

            I have attached an [updated sheet | ^Field Mapping Definitions - 20170414.xlsx] of data dictionary.

            This is an intermediate version and we are still working on this. On high level there 2 pending items

            1. Identify fields which are redundant.
            2. Description for remaining fields.

            Regards,
            Lalit Kumar

            CC : Cindy Wibbing,Umesh Kanade,Samir,Vijay Siddha,Satya

            Show
            lalit.kumar Lalit Kumar (Inactive) added a comment - Hello [ Abhay Patil , I have attached an [updated sheet | ^Field Mapping Definitions - 20170414.xlsx] of data dictionary. This is an intermediate version and we are still working on this. On high level there 2 pending items Identify fields which are redundant. Description for remaining fields. Regards, Lalit Kumar CC : Cindy Wibbing , Umesh Kanade , Samir , Vijay Siddha , Satya
            Hide
            lalit.kumar Lalit Kumar (Inactive) added a comment -

            Hello Abhay Patil,

            I have attached updated data dictionary .

            During the process we have identified 55 fields (marked in red color) which are not getting used in any feeds.

            Should we delete them from data dictionary (this document)? If yes, next question to evaluate would be "Should any changes (e.g. dropping these fields) be done in software as well. Your thoughts around this.

            Regards,
            Lalit Kumar,Satya

            Show
            lalit.kumar Lalit Kumar (Inactive) added a comment - Hello Abhay Patil , I have attached updated data dictionary . During the process we have identified 55 fields (marked in red color) which are not getting used in any feeds. Should we delete them from data dictionary (this document)? If yes, next question to evaluate would be "Should any changes (e.g. dropping these fields) be done in software as well. Your thoughts around this. Regards, Lalit Kumar , Satya
            Hide
            abhay.patil Abhay Patil (Inactive) added a comment - - edited

            Lalit Kumar -

            As for the 55 unused fields, if they show up as options in the system then they need to be safely removed from the system first.

            CC Satya Cindy Wibbing Chris Ellenberger Damion M Velasquez Van Nguyen Amit Thorve

            (Note: can you please delete the outdated attachments? There are five files that have names beginning with "Field Mapping". Of course one can see the dates, but it would be better if you could retain just the latest file.)

            Show
            abhay.patil Abhay Patil (Inactive) added a comment - - edited Lalit Kumar - As for the 55 unused fields, if they show up as options in the system then they need to be safely removed from the system first. CC Satya Cindy Wibbing Chris Ellenberger Damion M Velasquez Van Nguyen Amit Thorve (Note: can you please delete the outdated attachments? There are five files that have names beginning with "Field Mapping". Of course one can see the dates, but it would be better if you could retain just the latest file.)
            Hide
            lalit.kumar Lalit Kumar (Inactive) added a comment - - edited

            Hello Satya,

            As indicated above we can remove the 55 unused fields if they show up in the system.Requesting you to please create a separate ticket for removing the fields.

            Also, I have removed the old files uploaded by me. Please remove the following files uploaded by you.

            [^Field Mapping Definitions - 20160712.xls] and [^Field Mapping Definitions - 20170407.xls]

            Regards,
            Lalit Kumar

            Show
            lalit.kumar Lalit Kumar (Inactive) added a comment - - edited Hello Satya , As indicated above we can remove the 55 unused fields if they show up in the system.Requesting you to please create a separate ticket for removing the fields. Also, I have removed the old files uploaded by me. Please remove the following files uploaded by you. [^Field Mapping Definitions - 20160712.xls] and [^Field Mapping Definitions - 20170407.xls] Regards, Lalit Kumar
            Hide
            satyap Satya added a comment -

            Hi Vinayak,

            As discussed, can you please schedule to remove 55 mentioned fields. Link JIRA ticket to this parent ticket to keep track.

            Regards,
            Satya Prakash

            Show
            satyap Satya added a comment - Hi Vinayak, As discussed, can you please schedule to remove 55 mentioned fields. Link JIRA ticket to this parent ticket to keep track. Regards, Satya Prakash
            Hide
            Vinayak.Kulkarni Vinayak Kulkarni (Inactive) added a comment -

            Hi All,

            New jira WT-9922 is created to remove unused fields from fields mapping screen.

            Show
            Vinayak.Kulkarni Vinayak Kulkarni (Inactive) added a comment - Hi All, New jira WT-9922 is created to remove unused fields from fields mapping screen.
            Hide
            Cindy.Wibbing Cindy Wibbing (Inactive) added a comment -

            Hi Vinayak Kulkarni

            Can we get an updated Field Mapping Definitions lists.  We were looking for some of the fields that are now in Workterra but not on the 2017 list provided. 

            Also, from the Macros listing you provided we are trying to verify our interpretation of the macros so that we can make sure we are using them correctly on the file feeds.  Can you please review and make any additional notations associated with the last column on our interpretation.

             

            Field Name (Harbinger) Import / Export File Type Definition Nature Amenable to data transformation? Current EDI Interpretation/Comment
            Enrollment Plan Type Export Both This field will fetch 'Plan Type'  from the database table 'plan design.'  
             
             
             
             
             
            Direct Field From Database
            NO Pull Plan Type on Benefit.  Is this only for a single plantype selected?  Will it pull for multiple plan types selected on the template.
            Enrollment Enrolled IN Export Both Do not use as an updated field 'Member Enrolled In' Conditional Field (Macro) YES Pulls the enrollment for the employee record only even if defined on dependent subtemplates.  Ignores the enrollment associated with any dependent records.
            Enrollment Last Enrolled IN Custom Field Both This field will populate the last planned enrolled by the employee Conditional Field (Macro) NO Pulls the most recent enrollment for any member, EE, SP or Child.  Used to pull information on terminated records (i.e. Health Tiers, Effective dates.)
            Enrollment Spouse Enrolled In Custom Field   This property indicates whether the spouse is enrolled in benefit plan or not. Conditional Field (Macro) YES Only looks to the Spouse benefit.  Not subtemplate dependent but plan dependent.  Will look to see if the spouse is in the enrollment for plan in rule.  Can be used on columnwise Employee SubTemplate to look to Spouse enrollment for plan.
            Enrollment Member Enrolled IN Export Both This property indicates whether a member (employee, spouse, child) is enrolled in a benefit plan or not. Conditional Field (Macro) YES Subtemplate dependent not plan dependent.  Will look to see if the the member is in the enrollment for plan in rule engine based on the subtemplate the rule is defined on.  Member Enrolled IN on Spouse Subtemplate looks to whether the Spouse is enrolled on the plan, Member Enrolled IN on Employee Subtemplate looks to whether the Employee is enrolled on the plan and Member Enrolled IN on Child Subtemplate looks to whether the Child is enrolled on the plan.
            Enrollment  Member Enrolled In Benefittype Export     Conditional Field (Macro)   ?
            Enrollment  Child Enrolled IN Custom Field  Both This property indicates whether the child is enrolled in benefit plan or not. Conditional Field (Macro) YES Only looks to the Child benefit.  Not subtemplate dependent but plan dependent.  Will look to see if the child is in the enrollment for plan in rule.  Can be used on columnwise Employee SubTemplate to look to Child enrollment for plan.

            Thanks!

            Cindy

            Show
            Cindy.Wibbing Cindy Wibbing (Inactive) added a comment - Hi Vinayak Kulkarni Can we get an updated Field Mapping Definitions lists.  We were looking for some of the fields that are now in Workterra but not on the 2017 list provided.  Also, from the Macros listing you provided we are trying to verify our interpretation of the macros so that we can make sure we are using them correctly on the file feeds.  Can you please review and make any additional notations associated with the last column on our interpretation.   Field Name (Harbinger) Import / Export File Type Definition Nature Amenable to data transformation? Current EDI Interpretation/Comment Enrollment Plan Type Export Both This field will fetch 'Plan Type'  from the database table 'plan design.'             Direct Field From Database NO Pull Plan Type on Benefit.  Is this only for a single plantype selected?  Will it pull for multiple plan types selected on the template. Enrollment Enrolled IN Export Both Do not use as an updated field 'Member Enrolled In' Conditional Field (Macro) YES Pulls the enrollment for the employee record only even if defined on dependent subtemplates.  Ignores the enrollment associated with any dependent records. Enrollment Last Enrolled IN Custom Field Both This field will populate the last planned enrolled by the employee Conditional Field (Macro) NO Pulls the most recent enrollment for any member, EE, SP or Child.  Used to pull information on terminated records (i.e. Health Tiers, Effective dates.) Enrollment Spouse Enrolled In Custom Field   This property indicates whether the spouse is enrolled in benefit plan or not. Conditional Field (Macro) YES Only looks to the Spouse benefit.  Not subtemplate dependent but plan dependent.  Will look to see if the spouse is in the enrollment for plan in rule.  Can be used on columnwise Employee SubTemplate to look to Spouse enrollment for plan. Enrollment Member Enrolled IN Export Both This property indicates whether a member (employee, spouse, child) is enrolled in a benefit plan or not. Conditional Field (Macro) YES Subtemplate dependent not plan dependent.  Will look to see if the the member is in the enrollment for plan in rule engine based on the subtemplate the rule is defined on.  Member Enrolled IN on Spouse Subtemplate looks to whether the Spouse is enrolled on the plan, Member Enrolled IN on Employee Subtemplate looks to whether the Employee is enrolled on the plan and Member Enrolled IN on Child Subtemplate looks to whether the Child is enrolled on the plan. Enrollment  Member Enrolled In Benefittype Export     Conditional Field (Macro)   ? Enrollment  Child Enrolled IN Custom Field  Both This property indicates whether the child is enrolled in benefit plan or not. Conditional Field (Macro) YES Only looks to the Child benefit.  Not subtemplate dependent but plan dependent.  Will look to see if the child is in the enrollment for plan in rule.  Can be used on columnwise Employee SubTemplate to look to Child enrollment for plan. Thanks! Cindy

              People

              Assignee:
              Vinayak.Kulkarni Vinayak Kulkarni (Inactive)
              Reporter:
              satyap Satya
              Account Executive:
              Cindy Wibbing (Inactive)
              Developer:
              Lalit Kumar (Inactive)
              QA:
              Hrishikesh Deshpande (Inactive)
              Votes:
              0 Vote for this issue
              Watchers:
              5 Start watching this issue

                Dates

                Created:
                Updated:
                Resolved:

                  Time Tracking

                  Estimated:
                  Original Estimate - 8h Original Estimate - 8h
                  8h
                  Remaining:
                  Remaining Estimate - 0h
                  0h
                  Logged:
                  Time Spent - 47.75h
                  47.75h