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
Problem description and business impact 1) OOTB payments processing reassesses the Provider Attendance product delivery case each time a Roster Line Item is approved. When several Roster line items across all providers are submitted around the same time, this could result in a huge number of reassessments being triggered. This would adversely impact the performance of the online application as each reassessment triggers a new deferred process. 2) Significant custom processing needs to happen (related to funds management) on the completion of payment processing for each Roster Line Item. Adding these on the back of reassessments would further impact the performance of the online application, NC FAST's implementation of Curam Child Care would make use of Provider Attendance payments to pay child care providers. The submission of Roster Line Items by all the providers are expected to be concentrated towards the end of each month for payment towards services provided in the previous months. NC would need support for generating the provider payments in batch mode for the following reasons, 1) OOTB payments processing reassesses the Provider Attendance product delivery case each time a Roster Line Item is approved. When several Roster line items across all providers are submitted around the same time, this could result in a huge number of reassessments being triggered. This would adversely impact the performance of the online application as each reassessment triggers a new deferred process. 2) Significant custom processing needs to happen (related to funds management) on the completion of payment processing for each Roster Line Item. Adding these on the back of reassessments would further impact the performance of the online application, NC would require a Provider Attendance batch (or a set of batches) which would, 1) Reassess each Provider Attendance product delivery case once for all Roster Line Items that were approved on that day 2) Provide hook points to add custom post processing on the generation of Financial Component corresponding to each Roster Line Item.
Customer Name | North Carolina - Dept of Health and Human Services |
Hi Kelli,
We have evaluated request 1 and have determined that it cannot be implemented at this time as it does not align with our current roadmap strategy and it is therefore not something that we plan to address in-product.
However on request 2 (provide hook points), we would require more information on this before assessing it further. We would need to know what details you expect here and what kind of post processing is intended.
Could you please submit this request via a new RFE as this is separate to request 1.
Thank you for your interest in the Cúram product.
Eloise O'Riordan, Cúram SPM Offering Management tea
Thank you for this enhancement request. We will evaluate this request.