Users should have the ability to merge case data

Hi Amber,

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

In addition to the above configuration and customization points, there is functionality in Child Welfare that helps to meet your requirements if client merge is completed within a Child Welfare case (Intake, Investigation, or Ongoing Case).

If we take the Investigation Case as an example, there is an application property, curam.cfss.ccsInvestigation.participantMerge, that determines whether the concernRoleID of a prospect person that was merged with a registered person within the Investigation case needs to be updated to have the registered person displayed as the case participant instead of the prospect person within the Investigation case. These properties are documented in the KC in the following section: https://www.ibm.com/support/knowledgecenter/SS8S5A_7.0.5/com.ibm.curam.content.doc/CFSSConfig/c_CFSSCONFIG_Newappendix1PropertyAdministrationSettings1.html

An example scenario:
Register a child
Create a CPS Intake
Create a new Intake Participant and enter details similar to that of the registered child
On the Potential Matches step in the New Participant wizard, the system will return the child registered in step 1 as a possible match
In the 'Exact or Probable' column, select 'Probable'
The Intake Participant will be registered as a prospect person
Complete the Intake, recommend for 'Screen In', approve, and create an Investigation case
Within the Investigation case, navigate to the Participants page and expand the row for the Intake Participant
On the Probable Matches tab select the 'Match' function
In the 'Mark Duplicate' wizard that is displayed, merge the two clients
The Intake Participant has now been updated to be the original child

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 - Functionality
Source - Other

For recording keeping, the previous attributes were:
Brand - Watson Health
Product family - Cúram Social Program Management
Product - Child Welfare
Component - Functionality
Source -

Hi Michael,

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,
Laura Sanghi, Cúram SPM Offering Management team