WORKTERRAProject Type: software

WORKTERRA

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

          relates to

          Enhancement - An improvement or enhancement to an existing feature or task. WT-8875 City of Durham > HR Simplified COBRA > Custom Event > Dependents of Retirees Turning 65

          • Medium - Has the potential to affect progress.
          • Closed

            Activity

            Ascending order - Click to sort in descending order
            Hide
            Permalink
            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
            Permalink
            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.
            Hide
            Permalink
            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
            Hide
            Permalink
            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.

              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