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 Mar 4, 2020

RELATED IDEAS

OOTB Class ProspectPersonMappingBean is not extensible

The State of Missouri has a requirement to remove duplicate SSN and assign preferred contact method to other household members also (including a non Applicant) other than primary.
To accomplish that, there is a need to map the value of 'preferredContactMethod' and 'nonApplicantSSN' along with other fields done by OOTB in curam.workspaceservices.mappingbeans.impl.ProspectPersonMappingBean class.

There is also a need to update the mapping for Address fields for each participant submitted in the application Case .
OOTB have a mapping done in the method getAddressData() as:

fieldDetails.addressLine1 = "";
fieldDetails.addressLine2 = primaryMailingAddress.getAttribute("street1");
fieldDetails.addressLine3 = primaryMailingAddress.getAttribute("street2");

whereas the address element mapping should be like:

fieldDetails.addressLine1 = primaryMailingAddress.getAttribute("street1");
fieldDetails.addressLine2 = primaryMailingAddress.getAttribute("street2");

Customer Name Missouri
  • Attach files
  • Guest
    Reply
    |     Oct 7, 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
    |     Jun 5, 2020

    Hi Maribeth,

    We believe there are existing extension points that may satisfy your requirements here.

    1) For socialSecurityNumber and contact preferences, these attributes can be re-mapped to the required datastore attributes (e.g. nonApplicantSSN to ssn) prior to starting the mapping process via one of these extension points:
    - curam.workspaceservices.intake.impl.IntakeApplicationMappingEvents.preCreateCasesInCuram(IntakeApplication)
    - curam.workspaceservices.intake.impl.IntakeApplication.IntakeApplicationEvents.preMapDataToCuram(IntakeApplication)

    Also, after persons are registered, further data can be mapped to the Participant Data Case based on information in the Datastore via the following extension point:
    - curam.workspaceservices.applicationprocessing.impl.ConcernRoleMappingStrategy.updateConcernRoleFromDataStore(Entity, ConcernRole)


    2) For address mapping, code in ProspectPersonMappingBean will look up curam.workspaceservices.applicationprocessing.impl.AddressMappingStrategy and call getAddressData() on that class.

    OOTB the curam.healthcare.intake.impl.HCRUSAddressMappingStrategy is the strategy used.

    However, a custom implementation of curam.workspaceservices.applicationprocessing.impl.AddressMappingStrategy can be created which should address the requirements here.

    Please let me know if this extra information is sufficient to meet your requirements.

    Thank you,
    Shane McFadden, Cúram SPM Product Management team

  • Guest
    Reply
    |     Mar 5, 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