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
Currently, the Invoice Search uses the façade curam.cpm.facade.impl.ServiceInvoice.
searchServiceInvoiceDetails() which then calls another facade BPO curam.
cpm.facade.impl.ServiceInvoice.searchServiceInvoice(). If only invoice status has been mentioned as the search criteria for invoice search, searchServiceInvoice() method calls serviceInvoiceDAO.listAllActiveServiceInvoices() to fetch all the service invoices in the system. Then iterate through all these service invoices and for each service get the service invoice derived status which in turn fetch all valid service line items associated with this invoice. In this case there is a potential performance problem depending on how many invoices there are with the status selected as it's first fetching all the service invoices and then for each invoice fetching associated line items to get the derived status and then compare this derived status with incoming status.
We are requesting the following enhancement. As a suggestion, Instead of using derived status check during the invoice search shouldn't system preserve the derived status at service invoice level once any changes to any line item happens and when search, directly search the service invoices based on preserved derived status.
Refer to closed PMR 80502999649
Customer Name | Saskatchewan - Ministry of Social Services |
Hi Amber,
We have evaluated your request and have determined that it cannot be implemented at this time.
Looking at the history of requests in this area we understand you have already made a customization to this search area so that the Invoice Status will always be used in conjunction with
other search criteria so that potential performance issues are avoided.
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 - Provider Management
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 Amber,
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