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 Amber,
We acknowledge that this enhancement request has been accepted for consideration. It may not be delivered within the release currently under development however the theme is aligned with our current multi-year strategy and will be considered for a future release.
IBM may consider and evaluate any RFE Community feedback for this request through activities such as voting.
IBM will update this request in the future.
Thank you for your interest in the Cúram product.
Shane McFadden, Cúram SPM Product Management team
Additional information for Business Impact: We have multiple services with end dates and multiple with no end date. When the end dates ones display in the search result it requires the user has to analyze which services to select and which ones not to. Since the end dates are not required the user then has to un select these not applicable services which creates a great deal of extra time for the workers.
Once our business end dates a service we either create a new service or that service is no longer applicable. Therefore we would never need to back date a service that has been end dated in the application which is why we want the option to make the end dated services not visible in the application once they have been end dated. We would never have a business scenario where we would need to back date as we would use one of the other non end dated services.
Hi Amber,
In order to evaluate your request further, we require that you provide more business background information.
With the current functionality provided in the product, service deliveries with service dates in the past can be created and authorized, therefore the search needs to return end dated services for selection.
An example is if a service has been end-dated effective 9/30/2018 and a caseworker needs to authorize a service delivery for the delivery of services that occurred on 9/29/2018.
OOTB we have a validation message on the Schedule page of the Create Service wizard that ensures that the dated of service aligns correctly with the effective period of the service. We have attached a screenshot that shows an example.
In your implementation do you not make use of the OOTB functionality that allows a service delivery to be back-dated, and if not can you provide a business scenario as to why this is the case?
Thank you,
Shane McFadden, Cúram SPM Product Management team
Attachment (Description)
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