Shape the future of Curam!
We invite you to shape the future of Curam, 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 Curam team to refine your idea
Help Curam prioritize your ideas and requests
The Curam 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
Payments from multiple cases are frequently made to a single participant who is a nominee on those multiple cases in social services organizations. OOTB, this occurs for the Registered Person and may more frequently occur for Employers. In addition, organizations set other Participant types as nominees to take advantage of nominee-specific functionality not available with third party deductions (See RFE [RFE 1 – ‘External Party’ Participant as Nominee]), increasing the frequency of a single Participant being set as a nominee on multiple cases.
Currently, Curam does not support the synchronization of payment information from the Participant to various cases on which the Participants acts as a nominee, resulting in manual effort to update individual nominee information, including delivery patterns, bank account details, and addresses.
In ESDC, there are multiple Participants who acts as nominees on thousands of cases. Changes in Delivery Patterns are expected for these participants are expected post go-live and in the years thereafter, necessitating manual updates on up to 25,000 cases rather than a few dozen participant records.
Customer Name |
ESDC |
Market Segment |
WH Government |
Type of Request |
Customer Requirement |
Market Opportunity Customers who include a single Participant as a Nominee on multiple cases. |
CURAM:Workarounds + Proposed Solution
The following functionality is not available, which would significantly reduce manual effort associated with updates made to participants who are also nominees on multiple cases:
Highest Priority - Ability to modify the nominee delivery pattern across multiple cases simultaneously – e.g., switching from Check to Direct Deposit. For ESDC
Ability to modify the bank account on the participant, and have this reflected across multiple nominee records for the participant
Note: ESDC accepts future-dated changes (e.g., someone informing the organization of a future change to a bank account); currently, entering a future-dated change on the participant will not be reflected on the nominee
Ability to add a new address for a participant and end the old one, and have this reflected across multiple nominee records for the participant
Note: A workaround exists for this (editing an address rather than ending an old address and creating a new one; however, this is not preferred by the customer)
Note that updates like this do not permit future-dated evidence changes – e.g., the organization learning that someone will move in the future. Rather than being able to enter future-dated changes, this workaround forces the organization to wait until the day of the move to make an update.
The solution should permit updates across multiple nominee records but should not force this – i.e., some flexibility should be provided. For example – a participant may have different preferences for delivery patterns when acting as a nominee on different programs, even when they are a nominee on multiple benefit cases for that program.
Customer Name | ESDC |
Persona Based Summary
The solution should permit updates across multiple nominee records but should not force this – i.e., some flexibility should be provided. For example – a participant may have different preferences for delivery patterns when acting as a nominee on different programs, even when they are a nominee on multiple benefit cases for that program. |
|
Market Segment | Health & Human Services |
Type of Request | Idea |
Market Opportunity
Customers who include a single Participant as a Nominee on multiple cases. |
|
RFP Due Date (If Applicable) | May 31, 2024 |
Usage frequency + #/type of users impacted
The solution should permit updates across multiple nominee records but should not force this – i.e., some flexibility should be provided. For example – a participant may have different preferences for delivery patterns when acting as a nominee on different programs, even when they are a nominee on multiple benefit cases for that program. |
|
CURAM:Workarounds + Proposed Solution
The following functionality is not available, which would significantly reduce manual effort associated with updates made to participants who are also nominees on multiple cases:
|
Hi Benoit,
We have reviewed your enhancement suggestion.
Based on the information provided, our understanding of your request is as follows:
provide the ability to understand the potential impact to nominee records on active benefit delivery cases when changes are made to payment information at participant level, and how to make it easier to apply these changes to some or all of the nominee records
The theme is aligned with our current multi-year strategy for our product, and we have accepted your suggestion as a consideration for a future release. Not all items under consideration will make it into a release. As plans are confirmed, you will be notified when a specific release includes this enhancement.
Thank you for taking the time to share your ideas with us. We are committed to involving our users in building our product roadmap and appreciate your suggestions.
Regards,
Angela Brady, Cúram Product Management Team
Hi Angela and Benoit, I believe this idea has some overlapping concepts with the following: SOCPM-I-1217. Angela, thanks for the response on that one.
Dean
Hi Benoit,
Thank you for taking the time to share your ideas with us. We are committed to involving our users in building our product roadmap and appreciate your suggestions.
We will review the information you have provided and get back to you within 30 days. If additional details are required to complete our evaluation, we will send you a request for more information.
Thank you,
Angela Brady, Cúram Product Management Team