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 May 5, 2016

Intake does not support changes to existing evidence held

When an application is completed online (or even internally), once submitted, an AC is created and all the info inserted as new evidence records which then remain in an 'in edit' state until the application is authorised. This process works fine for brand new applications but not for scenarios where customers are already registered on the system.
E.g.
Create a new application online and as part of that process, pre-populate it with existing information we have on the client e.g. gender, dob, address, income etc. Pre-populating allows caseworkers to verify if the information we have already is valid or is still correct. Let�s say the client decides to change their gender - they can change the details in place. On the script, we may also ask, 'From what date did your gender change?'
When this application is submitted, this change to existing information isn't supported - all information from an intake script gets mapped to evidence on a newly created application case. The evidence remains in edit - as the evidence is an insert, there can be no 'effective date of change' captured as there is no record to succeed it.
This is a problem for customers because the caseworkers can't even update this.
Impact: Once the application case is authorised, the evidence will get shared onto a case - the gender in this case, is shared to the person record and because it doesn't have an 'effective date of change', the incoming evidence will be handled as a correction. For the caseworker, when they view the gender record, they would have the history showing the previous gender but the change that occurred would be a correction to the original value - this means that any info on when this occurred from is lost.

Customer Name New Zealand MSD
  • Attach files
  • Guest
    Reply
    |
    Aug 24, 2016

    Hi Sriramganesh,

    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.
    Eloise O'Riordan, Cúram SPM Offering Management team
    You can find more information on the RFE process here

  • Guest
    Reply
    |
    Jun 10, 2016

    Creation of RFE from legacy PMR 31,081,999,796