Skip to Main Content
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,

  1. Post an idea

  2. Upvote ideas that matter most to you

  3. 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

Status Delivered
Categories Income Support
Created by Guest
Created on Feb 26, 2016

Duplicate Food Benefit Issuance

DC's expectation is for the duplicate PDC validation to include closed PDCs, for the periods where the member was included in the assistance unit and benefits were issued.

This should be considered on eligibility checks on the Income Support Application and Income Support IC, and PDC Determination assessment/reassessment. If a member has been counted toward a benefit that has been issued, then they should not be eligible, again, to be counted toward benefit for the same period and product. Additionally, the expectation is that duplicate PDC validation would also occur when a closed PDC is reactivated. In the example provided in 'Duplicate Benefits.doc' (sections 14-17), DC's expectation would be for the second application to show the client ineligible for September, October, and the prorated portion of November (which the Overpayment did not cover). Also, when the closed PDC was reactivated (sections 32-33), validation should identify that there is a member that is already included in another PDC which is not closed. If the PDCs are associated to separate ICs, then the case worker should manage the appropriate evidences (household member etc). If the PDCs are associated to the same IC, then I don't think there is a valid scenario to reactivate a closed PDC when another PDC for the same product exists and is not closed.

There could be several scenarios for a PDC to be closed (eg a verification not provided with a specific time frame, the client becomes ineligible, the client requests for benefits to end) There is not a business requirement to re-apply and create a new PDC, which overlaps the closed PDC. There is also not a business requirement to reactivate a closed PDC, when one or more members are on an active PDC. This is a loop hole in the system, which allows the case worker to do this by error or intentional misconduct.

The business requirement is that a client cannot receive duplicate benefits, where they are counted toward a benefit for the same period and product. The only exception is for victims of domestic violence that leave the home and become a resident of a shelter for battered women and children. This requirement is being stressed since the loop hole does exist, and the federal FNS audits have a zero tolerance for this occurrence.

Customer Name IBM Corp
  • Attach files
  • Guest
    Reply
    |
    Jul 3, 2018

    Hi Richard,

    We are happy to inform you that your enhancement request has been delivered in the new release of IBM Cúram Social Program Management, version 7.0.3.0.

    Your requirement to prevent an individual from receiving duplicate benefits, where they are counted toward a benefit for the same period and product, has been delivered in the concurrent eligibility enhancement delivered in version 7.0.3.0.

    Administrators can now use report functions to monitor that no instances of concurrent eligibility periods occurred and to identify instances of concurrent eligibility in Food Assistance and Cash Assistance and for custom products.

    For more information on this, see the Knowledge Center at: https://www.ibm.com/support/knowledgecenter/SS8S5A_7.0.3/com.ibm.curam.content.doc/IncomeSupport/c_INCSPRT_MonitoringConcurrentEligibility.html

    We hope that this addition to the product will meet your requirements sufficiently.

    I will now close this ticket as delivered.

    Thank you for your interest in the Cúram product.
    Eloise O'Riordan, Cúram SPM Offering Management team

  • Guest
    Reply
    |
    Jul 7, 2016

    This is RFE has been recommended as a candidate for future release.

    John Sweeney
    Offering Manager - Social Programs