End Dated Services should not display in the Search Results

Good afternoon,

Agreement reached in a meeting between Curam and Linkin team on March 28th 2025, was to close out these lower priority ideas and instead the high priority ideas (top 1-6 ideas discussed) have been identified for consideration in future roadmap.

Although we will not be addressing this item in the near term, your suggestion will be available for future consideration. This request will be closed, and we will not be taking any further action. 

Thank you for taking the time to share your ideas with us. Although we cannot pursue all the submitted suggestions, we are committed to involving our users in building our product roadmap and appreciate your ideas.

Regards,

Angela Brady, Cúram Product Management Team

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