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

City of Durham > HR Simplified COBRA > Custom Event Request > How to Achieve?

    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
    • Company:
      City of Durham
    • Module:
      BenAdmin - Export
    • Severity:
      Simple

      Description

      Hello,

      We received a request from the client and broker to include a new custom event for COBRA.

      Note from the broker:

      I have confirmed that the loss of health coverage for dependents’ of retirees that are terminated from retiree coverage for the reason of age (Medicare eligibility at age 65) are eligible for a 36 month COBRA offer. The retiree is not eligible for an offer. Only the dependents are eligible.

      This client is utilizing old COBRA event approach, but i feel this dependent type event will still not be able to be configured through Event Builder.

      Can i please get insight into how we are to achieve this event and report to the COBRA vendor?

      Thanks,
      Chris

      cc Amit Thorve Vinayak Kulkarni Rohan J Khandave Ganesh Sadawarte

        Attachments

          Issue Links

            Activity

            Chris.ellenberger Chris Ellenberger created issue -
            Hide
            amitthorve Amit Thorve (Inactive) added a comment -

            Chris Ellenberger If I understand this correctly, client want to enrollment dependents of retired employees in COBRA plans but not the employee. As per my understanding we need to add these dependents as employees of the system to achieve the same. This cannot be handle with the event builder.

            Cindy Wibbing Please comment if you think otherwise.

            Debbie can provide her help on the same because she must have encounter such scenario before.

            Show
            amitthorve Amit Thorve (Inactive) added a comment - Chris Ellenberger If I understand this correctly, client want to enrollment dependents of retired employees in COBRA plans but not the employee. As per my understanding we need to add these dependents as employees of the system to achieve the same. This cannot be handle with the event builder. Cindy Wibbing Please comment if you think otherwise. Debbie can provide her help on the same because she must have encounter such scenario before.
            Hide
            Vinayak.Kulkarni Vinayak Kulkarni (Inactive) added a comment -

            Hi Chris,

            As per our understanding,

            to create medicare cobra event builder we can use employee age, like from employee age less than 66 to greater than equal to 66

            This event will track all employees who will loose benefits due to age crosses 65, but problem here is, it will apply these event to all member who were enrolled into plan including employee, and it will transmit both employee and child for medicare event as it processed all dropped members for this event.

            We can make medicare cobra event name as blank using data transformation for employee row but we can not avoid employee row for this event as per current implementation.

            Please let us know if you have questions on this. Thanks.

            Show
            Vinayak.Kulkarni Vinayak Kulkarni (Inactive) added a comment - Hi Chris, As per our understanding, to create medicare cobra event builder we can use employee age, like from employee age less than 66 to greater than equal to 66 This event will track all employees who will loose benefits due to age crosses 65, but problem here is, it will apply these event to all member who were enrolled into plan including employee, and it will transmit both employee and child for medicare event as it processed all dropped members for this event. We can make medicare cobra event name as blank using data transformation for employee row but we can not avoid employee row for this event as per current implementation. Please let us know if you have questions on this. Thanks.
            vijays Vijay Siddha (Inactive) made changes -
            Field Original Value New Value
            Environment Production [ 10005 ]
            Issue Type Task [ 3 ] Support Activity [ 10301 ]
            Status New Request [ 10029 ] Open [ 1 ]
            Support Task Type Query Resolution [ 11205 ]
            Workflow WT_Features [ 34358 ] WT_Support [ 34412 ]
            Vinayak.Kulkarni Vinayak Kulkarni (Inactive) made changes -
            Assignee Vijay Siddha [ vijays ] Chris Ellenberger [ chris.ellenberger ]
            Resolution Done [ 10000 ]
            Status Open [ 1 ] Resolved [ 5 ]
            Vinayak.Kulkarni Vinayak Kulkarni (Inactive) logged work - 10/Mar/17 01:18 PM
            • Time Spent:
              3h
               
              <No comment>
            Chris.ellenberger Chris Ellenberger made changes -
            QA Chris Ellenberger [ chris.ellenberger ]
            Hide
            Chris.ellenberger Chris Ellenberger added a comment -

            Hello,

            We need to report only the dependents per the broker and vendor. Can i request an enhancement to cover this scenario. I am sure it will arise again. I suspect we need a way to achieve through old and new approach for COBRA.

            Should i open a new ticket for this? Please advise.

            Thanks,
            Chris

            cc Vinayak Kulkarni Amit Thorve Abhay Patil Cindy Wibbing

            Show
            Chris.ellenberger Chris Ellenberger added a comment - Hello, We need to report only the dependents per the broker and vendor. Can i request an enhancement to cover this scenario. I am sure it will arise again. I suspect we need a way to achieve through old and new approach for COBRA. Should i open a new ticket for this? Please advise. Thanks, Chris cc Vinayak Kulkarni Amit Thorve Abhay Patil Cindy Wibbing
            Chris.ellenberger Chris Ellenberger made changes -
            Assignee Chris Ellenberger [ chris.ellenberger ] Vinayak Kulkarni [ vinayak.kulkarni ]
            Chris.ellenberger Chris Ellenberger made changes -
            Resolution Done [ 10000 ]
            Status Resolved [ 5 ] Reopened [ 4 ]
            Hide
            Vinayak.Kulkarni Vinayak Kulkarni (Inactive) added a comment -

            Hi Chris,

            Yes, we need to create a new ticket and you can refer this ticket on that.

            As of now, we have already planned current ( sprint 25) and next sprint ( sprint 26). This will be taken under next to next sprint ( 27 ) which will start from 10th April. Hope this is fine.

            Show
            Vinayak.Kulkarni Vinayak Kulkarni (Inactive) added a comment - Hi Chris, Yes, we need to create a new ticket and you can refer this ticket on that. As of now, we have already planned current ( sprint 25) and next sprint ( sprint 26). This will be taken under next to next sprint ( 27 ) which will start from 10th April. Hope this is fine.
            Vinayak.Kulkarni Vinayak Kulkarni (Inactive) made changes -
            Assignee Vinayak Kulkarni [ vinayak.kulkarni ] Chris Ellenberger [ chris.ellenberger ]
            Resolution Done [ 10000 ]
            Status Reopened [ 4 ] Resolved [ 5 ]
            Vinayak.Kulkarni Vinayak Kulkarni (Inactive) logged work - 14/Mar/17 12:24 PM
            • Time Spent:
              1h
               
              <No comment>
            Vinayak.Kulkarni Vinayak Kulkarni (Inactive) made changes -
            Remaining Estimate 3h [ 10800 ]
            Original Estimate 3h [ 10800 ]
            Vinayak.Kulkarni Vinayak Kulkarni (Inactive) made changes -
            Remaining Estimate 3h [ 10800 ] 0h [ 0 ]
            Time Spent 3h [ 10800 ]
            Worklog Id 31070 [ 31070 ]
            Vinayak.Kulkarni Vinayak Kulkarni (Inactive) made changes -
            Time Spent 3h [ 10800 ] 4h [ 14400 ]
            Worklog Id 31082 [ 31082 ]
            Chris.ellenberger Chris Ellenberger made changes -
            Link This issue relates to WT-8875 [ WT-8875 ]
            Chris.ellenberger Chris Ellenberger made changes -
            Status Resolved [ 5 ] Closed [ 6 ]
            Transition Time In Source Status Execution Times
            Vijay Siddha (Inactive) made transition -
            New Request Open
            11h 8m 1
            Vinayak Kulkarni (Inactive) made transition -
            Open Resolved
            25s 1
            Chris Ellenberger made transition -
            Resolved Reopen
            3d 5h 38m 1
            Vinayak Kulkarni (Inactive) made transition -
            Reopen Resolved
            13h 3m 1
            Chris Ellenberger made transition -
            Resolved Closed
            1d 13h 46m 1

              People

              Assignee:
              Chris.ellenberger Chris Ellenberger
              Reporter:
              Chris.ellenberger Chris Ellenberger
              QA:
              Chris Ellenberger
              Votes:
              0 Vote for this issue
              Watchers:
              3 Start watching this issue

                Dates

                Created:
                Updated:
                Resolved:

                  Time Tracking

                  Estimated:
                  Original Estimate - 3h Original Estimate - 3h
                  3h
                  Remaining:
                  Remaining Estimate - 0h
                  0h
                  Logged:
                  Time Spent - 4h
                  4h