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

Add a new idea Subscribe
Status Not under consideration
Categories Social Program Management Platform
Created by Guest
Created on Jun 24, 2020

RELATED IDEAS

CLIENT has a requirement to remove duplicate SSN and find person based on custom identifier

CLIENT has a requirement to remove duplicate SSN and find person based on custom identifier while processing people during the creation of Participant and Cases when mapping is done from DataStore to Curam.Additionally MO need to customize the data mapping for the application cases which are from Famis To MEDES for Annual Review Auto Conversion.
However, no hookpoint currently exists for DataMapperImpl to allow such a customization to be made compliantly. Due to lack of compliant way to customize DataMapperImpl, MO project have used the decompiled copy of the class and customize the method processPeople(), createParticipantsAndCases() and mapFromDataStoreToCuram() to meet the requirement.

Customer Name Missouri
  • Attach files
  • Guest
    Reply
    |     Nov 25, 2020

    Hi Maribeth,

    We have not received the additional information we previously requested from you that would allow us to fully understand and evaluate your enhancement request. Since we have not received the information within the 30 day timeframe, we are closing this request.

    If you are able to provide the additional information in the future, please open a new enhancement request and we will be glad to review. We do appreciate the time you take to share your ideas with us and utilize your inputs to improve our product offering.

    Thank you,
    Shane McFadden, SPM Offering Management team
    You can find more information on the request process here.

  • Guest
    Reply
    |     Sep 11, 2020

    Hi Maribeth,

    We have reviewed your enhancement suggestion and require more information to properly understand the issue and the business scenario you are trying to support.

    We would like to get some clarification on the business problem to be addressed here.

    The steps given are from within the caseworker application when a caseworker is creating applications on behalf of citizens. Is the business problem specific to when a caseworker creates an application for a citizen? Are you using a portal for a citizen to create applications online and if so, is the handling duplicates as expected?

    The use case outlined appears to arise when a second application is created before the first application is authorized and both these application cases can contain the same SSN.
    The system currently allows the SSN Details evidence to be duplicated across applications, but catches it later in the process, i.e.
    If the first application is authorized the SSN is shared for the first applicant and when the user attempts to authorize the second application, authorization is prevented and the following validation message is displayed "The identification details entered already exist for another Person. Please correct the details or review for duplicate Person details. "

    We do allow SSN Details to be duplicated on Application Case but prevent it beyond this. This, therefore, allows the application to be created representing the data as provided by the citizen.

    We would like to clarify if the request here to not allow the creation of duplicate SSN Details evidence in two application cases. If so, it would be good to understand why given the application case is intended to reflect the information entered about the applicant at the point in time the application is created?

    Please provide the requested information within 30 days so we may proceed with our evaluation. If we do not hear from you within that timeframe we will have to close the request due to insufficient information.

    Thank you,
    Shane McFadden, SPM Offering Management team
    You can find more information on the request process here.

  • Guest
    Reply
    |     Jun 25, 2020

    Hi Maribeth,

    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