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,
Post an idea
Upvote ideas that matter most to you
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
Hi Timothy,
We have evaluated your request and have determined that it cannot be implemented at this time.
There are customization points and configurations available for Client Merge functionality that we consider provide sufficient functionality in this area, therefore this is not an enhancement we plan to add to the product. Not all of these customization points and configurations are documented in the knowledge center, so we plan to update the KC in 7.0.7.0 release to ensure all the below information is correctly documented.
When a client is marked as a duplicate of another, a caseworker can view case-related information for the duplicate client along with the information of the master client, for example, when viewing a list of cases for the master client the caseworker is also able to view a list of the cases in which the duplicate client is a case participant. Information for the duplicate client is displayed when viewing the following information of the master client:
*Assessments
*Cases
*Communications
*Deductions
*Incidents
*Interactions
*Investigation
*Issue Cases
*Roles
*Service Plans
*Tasks
*Transactions
*Verifications
This allows the caseworker to view a clients’ duplicate records alongside the master records.
The application property curam.participant.clientmerge.softLinksEnabled controls the display of the case related information. The default value is ‘No’.
There are also events raised throughout the Client Merge processing that allows customization points:
1. At the end of “Mark as Duplicate” process(curam.core.sl.impl.ClientMerge.markDuplicate(MarkDuplicateCreateDetails)), the event CLIENTMERGE.MARKDUPLICATE is raised if there are cases (other than a Participant Data Case (PDC)) that are not closed for the duplicate client. Parameter passed to this event is: DuplicatedConcernRoleID
2. At the end of “UnMark as Duplicate” process (curam.core.sl.impl.ClientMerge.unmarkDuplicate(UnmarkDuplicateDetails)), the event CLIENTMERGE.UNMARKDUPLICATE is raised if there are cases (other than a Participant Data Case (PDC)) that are not closed for the duplicate client. Parameter passed to this event is: DuplicatedConcernRoleID
3. At the end of “Complete Merge” process (curam.core.sl.impl.ClientMerge.completeMerge(ConcernRoleDetailsForMerge)), one of two possible events is raised depending on the concern role type that is being merged:
CLIENTMERGE.MERGE_PERSON_TO_PERSON, parameters OriginalConcernRoleID and DuplicatedConcernRoleID
CLIENTMERGE.MERGE_PROSPECT_PERSON_TO_PERSON, parameters OriginalConcernRoleID and DuplicatedConcernRoleID
Your request may be resubmitted for consideration after 12 months from the date of decline.
Thank you for your interest in the Cúram SPM product.
Shane McFadden, Cúram SPM Product Management team
Due to processing by IBM, this request was reassigned to have the following updated attributes:
Brand - Watson Health
Product family - Cúram Social Program Management
Product - Social Program Management Platform
Component - Other
Source - Other
For recording keeping, the previous attributes were:
Brand - Watson Health
Product family - Cúram Social Program Management
Product - Income Support
Component - Other
Source - Other
Thanks look forward to hearing from you.
Thank you, Timothy. I will set up a call with IBM Lab Services to discuss this RFI along with several others and will then reach out if we need further clarification.
Thank you,
Sherry Byerly
Thanks that is helpful. We will bring this up to our dev team during our design sessions.
Hi Timothy,
The implementation of Client Merge functionality that is provided in product does not include an automatic merge of the cases in which the two clients are case members (which would include any case evidence) because any processing that might need to occur would depend upon the requirements of each customer and not be homogeneous. What was implemented in support of this requirement; however was a soft case merge feature that when configured (application property is "curam.participant.clientmerge.softLinksEnabled") displays all of the cases related to the duplicate client on the Cases page for the master client in a separate tab. A hook point also exists for use by customers at the end of the client merge process that can be used to implement additional processing if required.
Have you considered whether these two features would enable you to meet your business requirements?
Thank you.
Hi Timothy,
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,
Sherry Byerly, Cúram SPM Offering Management team