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 Jul 21, 2016

The eligibility for applicants on a closed PD case must not be determined and PD cases must not be created automatically

Problem title:
Issues with HCR-4413

Problem description:
The 6.0.5.5 release notes state:
http:www.ibm.com/support/docview.wss?uid=swg27042400

HCR-4413 - Prevent automatic reopening of product delivery cases when closed with a specific reason.

Previously, when a product delivery case with eligible applicants was closed, reassessment was triggered and the case was automatically reopened as the applicant was still eligible. The following enhancements are implemented so the product delivery cases are not reopened automatically and remain closed:
1. PD case closure is now enhanced to not reassess and reopen automatically when the case is closed with a specific reason, say 'Created in Error'.
2. The admin property curam.miscapp.productDeliveryReactivateClosedReason has been added to support the configuration of closure reasons based on which the PD cases are not to be reopened.
3. The Program Group logic is updated to not reuse PD cases that are closed with the configured reasons.
4. A hook is also added to the program group logic to support the implementation of custom logic if the closed cases have to be processed differently to what is supported by default.

This is replicated in the formal documentation. We consider this incorrect and believe it should re-assess and reconcile (i.e. grey box re-assessment as well as CER re-assessment) when the case is closed. However it should not re-open the case.

Why is the behaviour still different from CGISS (in terms of grey box we are aware there are no financial payments in HCR but we have custom issuance)

Business impact:
Potentially incorrect

Product release
6.0.5.5

Customer Name North Carolina - Dept of Health and Human Services
  • Attach files
  • Guest
    Reply
    |
    Aug 6, 2016

    Hi,

    We acknowledge that this is a valid enhancement request. It will be considered for inclusion in a future release of the product. Thank you for your interest in the Cúram product.

    Thanks,
    Eloise O'Riordan, Cúram SPM Offering Management team