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 17, 2020

Enact AES Explicity after mapping evidences and creation of Cases

System: IBM Curam Income Support

Actor: Department of Health Care Finance (https://dhcf.dc.gov/)

Description:

In Curam 7.0.6, we don't have API's to Enact AES workflow from the custom code during 'Check Eligibility' process. As part of the Process Intake Application workflow, at CreateParticipantsAndCases step, AES is enacted as a separate transaction that will pull/share the Participant Data Case (PDC) evidences on to Income Support IC.

However, in DCAS we have requirement to Register Person, Create Income Support IC, broker all the evidence from PDC to IC, Perform 'Check Eligibility', Authorize and create Product in one transaction as part of Batch Process.

The current AES process (Pull Workflow) hasn't completed the sharing of evidences from PDC to IC which is resulting in an error (PDC addresses evidence is not present in the IS application) during 'Check Eligibility' when performing all the steps mentioned in the requirement as a single transaction.

Customer Name District of Columbia - Washington
  • Attach files
  • Guest
    Reply
    |
    Mar 23, 2020

    Hi Chandra,

    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
    |
    Mar 8, 2020

    Hi Shane, My Sincere Apologies for the late response. I haven't got the email alert when the update was made on this RFE.

    D.C has a 1634 agreement with the SSA, clients who receive Supplemental Security Income are categorically eligible for Medicaid in the District. The Intake
    for SSI Recipients process begins with the system reading details of the SDX file received from SSA every day during the night and create an SSI Product
    Delivery Case using Curam Batch API.

    As part of this process, we're using Curam 7.0.6 version and seeing issues while performing 'Check Eligibility' on IncomeSupport IC as Participant Data Case pieces of evidence are not brokered to IC yet. Hence we're planning to use HCR AES Simulator that was shared by in this post
    (https://w3-connections.ibm.com/forums/html/topic?id=58ba81ca-5520-4ecf-b839-dabcbd26f209&ps=25)
    and had discussions with Paul Martin (paul.martin@ie.ibm.com) in this regard. Paul advised us to raise enhancement requests as these APIs are internal and assessment is required if they can be used via the Batch Program.

    Kindly please let me know if you need more information.

  • Guest
    Reply
    |
    Jan 31, 2020

    Hi Chandra,

    In order to evaluate your request, we require that you provide more detail so that we can fully understand your requirements.

    You have indicated that you are doing Register a Person, Create Application & Income Support IC, share evidences from PDC Case to IC, Perform Check Eligibility and Authorize and Activate PDC in one single transaction via batch process. We would like to better understand why these are running in a batch process? For example, batch is typically the approach taken for processing volumes and if that's the case here what is the setup in DC and are you processing volumes of person and application registrations through batch?

    If we do not receive this information within 30 days, this request will be closed.

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

  • Guest
    Reply
    |
    Jan 21, 2020

    Hi Chandra,

    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