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 Linas Jakucionis
Created on Feb 14, 2019

Provide UI capability and integration hook to perform the address search and validation in Curam (UIM, Dynamic Evidence, IEG)

There is a common requirement accross customers to perform address search/validation when a user (case worker) enters an address details (e.g. person registration, address modification, address details in evidence, provider address, etc.).

We do have access to our region specific APIs to search for the valid addresses.

The basic expectations are:

1. a user should be able to do a type ahead search for an address based on a partially entered address (similar to this: https://www.nzpost.co.nz/tools/address-postcode-finder/)
2. a user should be able to select an address returned from that search
3. a user should be able to continue with a user entered address when it cannot be found (but mark it as a non validated address)
4. a user should not be able to modify an address returned from the search results unless...
5. when updating a validated address a user should be forced to go through the cycle of search -> select validated or confirm that the details entered are correct even if the address cannot be validated -> save as validated or save as unvalidated address

We have already built similar functionality in our instance of Curam (without type ahead functionality).

Customer Name New Zealand MSD
  • Attach files
  • Guest
    Reply
    |
    Apr 2, 2019

    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.
    Shane McFadden, Cúram SPM Product Management team

  • Guest
    Reply
    |
    Feb 15, 2019

    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,
    Shane McFadden, Cúram SPM Product Management team