Skip to Main Content
Merative Ideas Portal

Shape the future of Merative!

We invite you to shape the future of Merative, including product roadmaps, by submitting ideas that matter to you the most. Here's how it works:

Post your ideas

Start by posting ideas and requests to enhance a product or service. Take a look at ideas others have posted and upvote them if they matter to you,

  1. Post an idea

  2. Upvote ideas that matter most to you

  3. Get feedback from the Merative team to refine your idea

Help Merative prioritize your ideas and requests

The Merative team may need your help to refine the ideas so they may ask for more information or feedback. The offering manager team will then decide if they can begin working on your idea. If they can start during the next development cycle, they will put the idea on the priority list. Each team at Merative works on a different schedule, where some ideas can be implemented right away, others may be placed on a different schedule.

Receive notification on the decision

Some ideas can be implemented at Merative, while others may not fit within the development plans for the product. In either case, the team will let you know as soon as possible. In some cases, we may be able to find alternatives for ideas which cannot be implemented in a reasonable time.


Merative External Privacy Statement: https://www.merative.com/privacy

Status Future consideration
Created by Guest
Created on Jan 29, 2020

EmployerSponserCoverageDataApplicationListener

Details about the issue

Detailed description of the issue

State of Missouri copied the OOTB class EmployerSponserCoverageDataApplicationListener to use additional attributes employeeContribution, frequencyContribution and lowestCostPlan for the entity TempEmployerSponsoredCoverage and to remove coverageEndDate attribute from the entities TempEmployerEnrolledSponsoredCoverage and TempEmployerSponsoredCoverage. As this class eclipses the OOTB EmployerSponserCoverageDataApplicationListener, a hookpoint is needed to customize the private methods createTempEmployerEnrolledSponsoredCoverage() and createTempEligubleSponsoredCoverage().


Detailed steps to reproduce the issue in an out-of-the-box environment

[As HCR case worker]
01) Register a person
02) From the tab action menu of the Participant Data Case, select 'New Application Form...'
03) Complete and submit the intake application
04) From the tab action menu of the Application case, select 'Check Eligibility...' and authorize the application.
05) Click 'Evidence' from tab navigation bar of Integrated case.
06) Create new evidence 'Employer Sponsored Coverage' under Income.

If the issue cannot be replicated in an out-of-box environment, describe the detailed steps that are necessary to help emulate the customized environment in order to highlight the underlying out-of-the-box issue

N/A

Details of any on-site investigations that have been done

N/A

Description of any workarounds / potential solutions that are being used

MO have previously worked around this issue by using the custom listerner class which eclipses the OOTB class of the same name - 'EmployerSponserCoverageDataApplicationListener' in the same package - 'curam.healthcare.intake.impl' to override its private methods createTempEmployerEnrolledSponsoredCoverage() and createTempEligubleSponsoredCoverage().

configreport.zip file created by running the Cúram configreport Ant target.

N/A

================================================================================

Details about the Impact of the Issue

Describe the business impact of the issue on the end user

Without the requested hookpoint, the State of Missouri's requirements cannot be compliantly implemented resulting in a maintenance burden due to non-compliant implementation.

When was the issue first identified?

N/A

How often does the issue occur?

On Creating a new evidence - Employer Sponsored Coverage of Integrated case.

Does the issue affect all users?

yes

================================================================================

Environment

Exact version of IBM Curam

v7.0.7

Type of environment

OOTB

Does this appear to be a regression?

No

Has the issue been replicated in another environment?

N/A

Details of any customizations that have been made in the affected area

N/A

Customer Name Missouri
  • Attach files
  • Guest
    Reply
    |
    Feb 12, 2020

    Hi Maribeth,

    We acknowledge that this enhancement request has been accepted for consideration. It may not be delivered within the release currently under development however the theme is aligned with our current multi-year strategy and will be considered for a future release.

    IBM may consider and evaluate any RFE Community feedback for this request through activities such as voting.

    IBM will update this request in the future.

    Thank you for your interest in the Cúram product.
    Shane McFadden, Cúram SPM Product Management team

  • Guest
    Reply
    |
    Jan 31, 2020

    Hi Maribeth,

    Thank you for your enhancement request.
    We require some further analysis to determine whether or not this enhancement can be considered in a future release.
    I will provide another response when our investigation is complete.

    Thank you,
    Shane McFadden, Cúram SPM Product Management team