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 Feb 13, 2018

Make it easier to avoid duplicate person registration

We need person registration enhancement to help users avoid registering duplicate persons.

Without good support from the system and having to deal with KPIs, some users rush through the process and registering a new person is sometimes much easier than identifying the right person record in the database.


Business impacts:

* financial - the same client may end up being paid twice.

* data quality and data processing time - the next time the organisation has to deal with the same person, it becomes even more difficult to identify correct person record.

* data quality and clean up - a special team is required to do clean up once the data is propagated from CMS to other backend systems.

Why existing OOTB solution is not sufficient?

Existing OOTB solutions such as merge person/mark person as duplicate/new Curam identity management module are not sufficient as all of them are geared towards clean up of duplicates post factum and they only work in Curam.

However, MSD (and I believe most other customers) integrate Curam with backend systems (such as job seeker DB, payment system, debt collections, data warehouse). Once the person is registered and published to other systems NONE of the OOTB solutions work to clean up / merge duplicate records. This type of clean up requires involvement of a special team which is familiar with intricacies and dependencies amongst multiple systems.

Some duplicate persons are registered through online applications process too.

Customer Name New Zealand MSD, Saskatchewan - Ministry of Social Services, South Carolina
  • Attach files
  • Guest
    Reply
    |
    Apr 26, 2018

    Hi Linas,

    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

  • Guest
    Reply
    |
    Mar 9, 2018

    Hi Linas,

    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,
    Eloise O'Riordan, Cúram SPM Offering Management team